Microsoft SCOM Security Technical Implementation Guide

Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

Microsoft SCOM Security Technical Implementation Guide

Overview

Version	Date	Finding Count (18)			Downloads
1	2021-03-15	CAT I (High): 7	CAT II (Med): 7	CAT III (Low): 4	Excel	JSON	XML

STIG Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Available Profiles

Classified	Public	Sensitive
I - Mission Critical Classified	I - Mission Critical Public	I - Mission Critical Sensitive	II - Mission Support Classified	II - Mission Support Public	II - Mission Support Sensitive	III - Administrative Classified	III - Administrative Public	III - Administrative Sensitive

Findings (MAC III - Administrative Sensitive)

Finding ID	Severity	Title	Description
V-237429	High	The Microsoft SCOM Service Accounts and Run As accounts must not be granted enterprise or domain level administrative privileges.	The Microsoft SCOM privileged Run As accounts are used to execute work flow tasks on target endpoints. A SCOM Run As account must only have the level of privileges required to perform the defined...
V-237425	High	SCOM Run As accounts used to manage Linux/UNIX endpoints must be configured for least privilege.	The Microsoft SCOM privileged Run As accounts are used to execute work flow tasks on target endpoints. A SCOM Run As account must only have the level of privileges required to perform the defined...
V-237424	High	Manually configured SCOM Run As accounts must be set to More Secure distribution.	The Microsoft SCOM privileged Run As accounts are used to execute work flow tasks on target endpoints. A SCOM Run As account creates an interactive log on session to perform its tasks. The...
V-237432	High	The Microsoft SCOM server must be running Windows operating system that supports modern security features such as virtualization based security.	Network devices running older but supported operating systems lack modern security features that mitigate attack surfaces. Attackers face a higher level of complexity to overcome during a...
V-237430	High	SCOM SQL Management must be configured to use least privileges.	Microsoft SCOM's SQL management requires a Run as solution because the local system account will not have the required permissions to monitor SQL. If the Run As account is created with elevated...
V-237438	High	The SCOM Web Console must be configured for HTTPS.	HTTP sessions are sent in clear text and can allow a man in the middle to recon the environment. The web console itself does not allow for administrative actions, so most of the risk associated...
V-237439	High	All SCOM servers must be configured for FIPS 140-2 compliance.	Unapproved mechanisms used for authentication to the cryptographic module are not validated and therefore cannot be relied on to provide confidentiality or integrity, and DoD data may be...
V-237423	Medium	Members of the SCOM Administrators Group must be reviewed to ensure access is still required.	When people leave their roles, their group memberships are often times not updated.
V-237427	Medium	The Microsoft SCOM Run As accounts must only use least access permissions.	The Microsoft SCOM privileged Run As accounts are used to execute work flow tasks on target endpoints. Run As Accounts are interactive logon sessions on a system. An attacker who has compromised...
V-237426	Medium	The Microsoft SCOM Agent Action Account must be a local system account.	The SCOM agent action account is the account agent used to perform tasks on an individual machine. By default, the action agent account is the local system account, but this can be configured to...
V-237436	Medium	The Microsoft SCOM server must use an active directory group that contains authorized members of the SCOM Administrators Role Group.	During the initial installation, SCOM grants the Builtin\Administrators group administrator rights to the application. This configuration will allow any local administrator to the SCOM server to...
V-237437	Medium	The default Builtin\Administrators group must be removed from the SCOM Administrators Role Group.	SCOM servers with default well-known operating system groups defined the SCOM Administrators Global Group may allow a local administrator access to privileged SCOM access.
V-237431	Medium	The Microsoft SCOM server must back up audit records at least every seven days onto a different system or system component than the system or component being audited.	Protection of log data includes assuring log data is not accidentally lost or deleted. Regularly backing up audit records to a different system or onto separate media than the system being audited...
V-237440	Medium	A host-based firewall must be configured on the SCOM management servers.	To prevent a DDoS, a firewall that inspects and drops packets must be configured.
V-237428	Low	The Microsoft SCOM administration console must only be installed on Management Servers and hardened Privileged Access Workstations.	The Microsoft SCOM management servers are considered high value IT resources where compromise would cause a significant impact to the organization. The Operations Manager console contains APIs...
V-237434	Low	If a certificate is used for the SCOM web console, this certificate must be generated by a DoD CA or CA approved by the organization.	Web certificates should always be signed by a trusted signer and never self-signed.
V-237435	Low	The Microsoft SCOM SNMP Monitoring in SCOM must use SNMP V3.	SNMP Versions 1 and 2 do not use a FIPS-validated Keyed-Hash message Authentication Code (HMAC). SCOM has the capability of monitoring all versions of SNMP. As such, SNMP 1 and 2 monitoring should...
V-237433	Low	SCOM unsealed management packs must be backed up regularly.	SCOM's configuration information is stored within unsealed management packs. Even without SQL backups, a catastrophic failure to SCOM can be recovered from quickly if the unsealed management packs...